Configurable communication infrastructure for event spaces

ABSTRACT

One embodiment provides a system for event space communication infrastructure, including: a plurality of mobile infrastructure devices; each of the plurality of mobile infrastructure devices being associated with one or more predetermined users; each of the plurality of mobile infrastructure devices comprising a wireless communication device that: broadcasts a unique identifier associated with a predetermined user; detects a response from at least one client mobile device; switches into a communication mode after detecting the response; and establishes data exchange with the at least one client mobile device. Other aspects are described and claimed.

BACKGROUND

Convention floor spaces, trade show venues and similar event spaces posechallenges with respect to providing a communication infrastructuretherewith. This is at least in part due to the fact that event spaceschange dynamically, e.g., vendor or booth locations change over thecourse of a convention or between events.

Typically, broad-coverage Wi-Fi® access or cellular networks are usedfor providing indoor or outdoor wireless communication capabilities insuch scenarios, but these networks tend to cover the entire event space(or large portions thereof) indiscriminately. Wi-Fi® access points orrouters are installed in fixed locations in an un-configured eventspace, which results in uneven coverage patterns. Moreover, the coveragepattern will often change unpredictably once the event space isconfigured for a particular event as temporary structures, signage, andeven people cause signal attenuation and reflection. Wi-Fi® is aregistered trademark of Wi-Fi Alliance in the United States and othercountries.

Conventionally, attendees at events have relied on wide area coveragewireless networks, e.g., Wi-Fi® or cellular networks, and turned to moretraditional solutions for targeted exchange of information. For example,conference attendees have Wi-Fi® access but still rely on leaving abusiness card with a booth or vendor of interest. In some cases,scanning a magnetic strip card are used to pass simple identifyinginformation. In order to obtain other information, e.g., locations ofvendors of interest, product information on items of interest, etc.,paper brochures or static maps are still provided.

BRIEF SUMMARY

In summary, an embodiment provides a system for event spacecommunication infrastructure, comprising: a plurality of mobileinfrastructure devices; each of the plurality of mobile infrastructuredevices being associated with one or more predetermined users; each ofthe plurality of mobile infrastructure devices comprising a wirelesscommunication device that: broadcasts a unique identifier associatedwith a predetermined user; detects a response from at least one clientmobile device; switches into a communication mode after detecting theresponse; and establishes data exchange with the at least one clientmobile device.

Another embodiment provides a method for event space communication,comprising: broadcasting, with a mobile infrastructure device, a uniqueidentifier associated with a predetermined user; detecting, at themobile infrastructure device, a response from at least one client mobiledevice; switching the mobile infrastructure device into a communicationmode after detecting the response; and establishing, between the mobileinfrastructure device and the at least one client mobile device, dataexchange.

A further embodiment provides a method for event space communication,comprising: providing, to a client mobile device, an applicationcomprising predetermined user information; receiving, from the clientmobile device, an indication of interest in at least one predetermineduser included in the predetermined user information; identifying, usinga processor, a predetermined user based on the indication of interest;providing, to the client mobile device, a unique identifier of thepredetermined user; and thereafter communicating, to a mobileinfrastructure device assigned to the predetermined user, a uniqueidentifier of the client mobile device.

A still further embodiment provides a mobile infrastructure device forevent space communication, comprising: a communication device thatbroadcasts a unique identifier associated with a predetermined user; aprocessor that detects a response from at least one client mobile deviceand switches into a communication mode after detecting the response; anda communication device that, after detecting the response from the atleast one client device, establishes data exchange with the at least oneclient mobile device.

For a better understanding of the embodiments, together with other andfurther features and advantages thereof, reference is made to thefollowing description, taken in conjunction with the accompanyingdrawings. The scope of the embodiments will be pointed out in theappended claims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates an example of broadcasting identification data frominfrastructure devices according to an embodiment.

FIG. 2 illustrates an example of data exchange between an infrastructuredevice and a client device according to an embodiment.

FIG. 3 illustrates an example method of communication between mobiledevices according to an embodiment.

FIG. 4 illustrates an example of a deployed communication infrastructurefor an indoor event space according to an embodiment.

FIG. 5 illustrates an example of a deployed communication infrastructurefor an indoor and outdoor event space according to an embodiment.

DETAILED DESCRIPTION

As used herein, a mobile infrastructure device is any mobile electronicthat may be temporarily deployed in an event space and exchange datawith other electronic devices. Examples of mobile infrastructure devicesinclude an infrared (IR) communication device, a Bluetooth®communication device, a Bluetooth® Low Energy (LE) communication device,a cellular communication device, a Wi-Fi® communication device, a radiofrequency identification (RFID) communication device, a near fieldcommunication (NFC) device, and combinations of the foregoing.Bluetooth® is a registered trademark of Bluetooth SIG, Inc. in theUnited States and other countries.

As used herein, a mobile infrastructure device may be deployed andcommunicate with other mobile infrastructure devices to form or join amesh network.

As used herein, a booth device is an example of a mobile infrastructuredevice that is assigned to an event vendor for use indoors or outdoors.

As used herein, a client mobile device is any electronic device thatcommunicates with a mobile infrastructure device. An example of a clientmobile device is a mobile phone.

As used herein, an event space is a floor space, a trade show venue, aconvention space, a room within a building, an outdoor space, acombination of indoor and outdoor spaces, or any space that employs atemporary or changing configuration for an event.

While various wide area network services provide generic wirelesscommunication capabilities (e.g., voice, texting, and Internet access)to an event space, these offer broad interconnectivity services, i.e.,coverage is provided for an entire room or floor of a conference center,a large area of outdoor space, a room within a building, etc. There isno granular linking of attendees (e.g., vendors and clients) becauseconventional infrastructure devices (e.g., Wi-Fi® hotspots, femto-cells,etc.) are not configured to distinguish between attendees that connectthereto. Additionally, conventional network approaches are static, wherethe infrastructure devices are static, i.e., remains in the same placeand configuration throughout the event.

This forces clients and vendors to rely on conventional (e.g.,paper-based) communication techniques. For example, in a typical tradeshow or conference, a vendor in a booth might wish to speak or interactwith a subset of potential clients. Likewise, clients are ofteninterested in only a subset of vendors or booths. Conventionally, suchattendees must rely on exchanging of business cards in order tocommunicate simple contact information. Additionally, clients must relyon paper or static electronic maps to locate vendor booths of interest.Furthermore, vendors are not aware of the itinerary of the clients, muchless their real-time location, and so must rely on conventionalcommunication techniques (emails, phone calls, etc.) to establishmeeting times. Still further, vendors often must wait until after aconvention or trade show has concluded to have access to metrics ofinterest, e.g., number of conference attendees, number of clients thatvisited the vendor's booth, etc.

Accordingly, embodiments provide systems, methods and products forimplementing a communication infrastructure that may be changed asnecessary, e.g., on the fly, such that a dynamic link between differentattendees is achieved.

An embodiment facilitates granular resolution of client and vendorlocations in real time using peer-to-peer wireless communicationsbetween mobile devices. Methods used to connect mobile devices caninclude infrared (IR) communication, Bluetooth® communication,Bluetooth® Low Energy (LE) communication, cellular communication, Wi-Fi®communication, radio frequency identification (RFID) communication, nearfield communication (NFC), and other communication techniques. In anembodiment, the peer-to-peer wireless communication is augmented by aconnection to a back end system and a broader network, e.g., theInternet.

The illustrated example embodiments will be best understood by referenceto the figures.

Referring to FIG. 1, an example embodiment is illustrated as implementedin an event space 101 such as a convention or trade show venue. Prior tothe event, a client 102 registers and downloads an application toconfigure the event experience. The application may be downloaded to aclient mobile device 103 of the client 102, such as a mobile phone thatincludes a wireless communication subsystem. As part of theconfiguration process, the client 102 will indicate preferences in termsof what other attendees (e.g., vendors) that the client 102 isinterested in. These other attendees (e.g., vendors) are added to a listby the client 102 within the application.

Thereafter, as the client 102 walks about the convention floor withinthe event space 101, signals 108, 109 are transmitted to the clientmobile device 103 from mobile infrastructure devices such as boothdevices 106, 107, located in vendor booths 104, 105, respectively. Basedon the configuration of the application running on the client mobiledevice 103, the client 102 may be notified by the client mobile device103 that the client 102 is in proximity to a vendor's booth that is ofinterest.

In the example illustrated in FIG. 1, if the client 102 had previouslyexpressed an interest in a vendor associated with vendor booth B 105,but had not expressed an interest in vendor booth A 104, the applicationrunning on the client mobile device 103 is configured to notify theclient 102 when the signal 109 is received by client mobile device 103,but not when the signal 108 is received by client mobile device 103.

The signals 108, 109 may be wireless beacon signals transmitted using astandardized protocol. For example, signals 108, 109 may be BluetoothLE® signals that are transmitted by Bluetooth LE® booth devices 106,107. In an embodiment, the signals 108, 109 contain a unique identifieror code such that client mobile device 103 may receive signals 108, 109and identify vendors using signals 108, 109.

In the non-limiting example of a Bluetooth LE® device, booth devices106, 107 comprise a 2.4 GHz system on chip design that operates aBluetooth LE® protocol and includes peripherals to interface withexternal devices. In one example, the system provides a radio frequency(RF) transceiver (e.g., a Bluetooth® 4.0 radio), and RAM memory foroperation. The booth devices 106, 107 include a microprocessor ormicrocontroller core and a programmable memory such as FLASH memory. Inone example, the booth devices 106, 107 include infrared (IR) generationcircuitry and provide digital received strength indicator (RSSI) data.The booth devices 106, 107 are powered directly by a battery, e.g., 3Vbattery, and are characterized by very low power usage. Bluetooth LE®devices are available from a variety of vendors including SiliconLaboratories and Texas Instruments.

The booth devices 106, 107 are distributed to vendors at registration orcheck-in time, where each booth device 106, 107 is associated with aunique vendor, vendor booth, etc. The signals 108, 109 are unique to thebooth devices 106, 107, respectively, i.e., permitting client mobiledevice 103 to distinguish between vendor booths 104, 105 using signals108, 109.

In an embodiment, the application running on client mobile device 103permits the client 102 to distinguish between large numbers of vendorsin a semi-automated fashion. Therefore, after the client 102 hasexpressed interests to the application running on client mobile device103, the client 102 is automatically notified only of those vendors heor she has an interest in.

The selection of or expression of interest in various vendors (or otherentities of interest) is facilitated by the application running onclient mobile device 103 in a variety of ways. For example, theapplication running on client mobile device 103 permits the client 102to select topic categories or to select vendors individually, with thetopic categories automatically adding various vendors to the client's102 interest list.

In an embodiment, if a client 102 has not configured the application, orif there are vendor booths (beacon or signaling devices) that have notbeen added to the interest list, the client 102 manually interacts withthe client mobile device 103 to express an interest in the vendor. Forexample, a client 102 interfaces with the client mobile device 103 torequest information proactively from a booth device 106 or 107, or aclient 102 reacts to a notification from the client mobile device 103 byexpressing interest, e.g., manually interfacing with client mobiledevice 103 to request more information from a booth device 106, 107.

If the client 102 has expressed an interest in a particular vendor, andthereafter is proximate to (within range of) that vendor's booth device106, 107, a communication protocol is established for exchange ofinformation between the client mobile device 103 and the vendor's boothdevice, e.g., booth device 107.

By way of example, illustrated in FIG. 2 is an example wirelesscommunication protocol according to an embodiment. As shown, a client202 configures the application running on client mobile device 203 toconsider vendor booth B indicated at 205 of interest. The vendor thatoperates vendor booth B 205 likewise registers and obtains a device,here booth device 207. The booth device 207 broadcasts a wireless beaconsignal, an infrared signal, etc., i.e., signal 210, including a uniquecode that has been associated with the vendor operating vendor booth B205.

As client 202 is within signal range of signal 210, client mobile device203 receives signal 210 and unique code contained therein. For example,booth device 207 is a Bluetooth® LE beacon device that transmits awireless beacon signal 210 that is received by a Bluetooth® radioresident on client mobile device 203. Client mobile device 203 in turndetermines the presence of a unique code within the signal 210. Thispermits client mobile device 203 to identify the vendor associated withvendor booth B, shown at 205. This identification is conducted locallyon client mobile device 203, e.g., by the application running on clientmobile device 203 and configured by client 202. This identification mayalso be conducted remotely, e.g., by communication between client mobiledevice 203 and another device, e.g., manager database 214, via wirelessnetwork communication link 213, or via telecommunications networkcommunication link 212. A combination of local and remote identificationmay be utilized.

If the unique code contained in signal 210 is that of a vendor for whichthe client 202 has expressed an interest, client mobile device 203notifies client 202 automatically that client 202 is proximate to vendorbooth B 205. Additionally, client mobile device 203 takes part in anautomated two-way communication protocol with booth device 207.

For example, client mobile device 203 transmits a signal 211 in order toacknowledge signal 210 and request that the two way communication beestablished. This permits the client mobile device 203 to identifyitself to the booth device 207. Furthermore, the client mobile device203 requests information from the booth device 207, e.g., electronicbriefcase documents, multimedia presentations, etc.

The two way communication is facilitated by a backend system comprisingmanager database 214 or other devices. For example, in order to obtaincertain data, client mobile device 203 is provided with a link orresource locator, communicated from booth device 207, which is used toobtain prepared materials of the vendor, e.g., multi-media presentationssuch as videos, audio files, etc. Alternatively, booth device 207communicates information directly to client mobile device 203. In anembodiment, different information may be distributed to different clientdevices, e.g., multi-media presentations such as videos, audio files,etc., may be provided to client devices in different languages accordingto preferences associated with the client devices, e.g., as determinedduring client device application configuration.

In FIG. 2, the client 202 has expressed interest in the vendor at vendorbooth B 205. In this case, the client 202 does not even need to stop atvendor booth B 205 to receive information from the vendor. All relevantinformation is provided to the client mobile device 203 as the client202 passes by the vendor's booth 205, whether in real time or at a latertime. This information can be delivered directly to the client mobiledevice 203 or delivered to a separate location (e.g., email address)identified by the client 202 during the application configurationprocess. No physical interaction between the client 202 and the vendorin vendor booth B 205 is necessary for the client mobile device 203 togather information of interest.

If the client 202 has not expressed an interest in the vendor associatedwith vendor booth B 205, and identified by booth device 207, and has nointerest in the information, products, goods, or services provided, noinformation is delivered to the client mobile device 203 as he or shepasses by vendor booth B 205.

In an embodiment, the application running on client mobile device 203validates what information has already been exchanged with or obtainedfrom booth device 207 on receipt of signal 210. If the client mobiledevice 203 has previously interacted with the vendor (e.g., has alreadywalked past vendor booth B 205), duplicate information exchanges isprevented.

Referring back to FIG. 1, as a client 102 moves throughout the event,each vendor's booth 104, 105 emits a signal 108, 109 (wireless beaconsignal, infrared signal, etc.) using booth devices 106, 107 to indicatepresence. During this part of the signaling process, booth devices 106,107 act as clients that continuously or intermittently emit a signal108, 109 that is unique to that vendor's booth (e.g., broadcasting an“advertisement” such as “I am here” coupled with a unique identifier).If a client mobile device 203 passes by and there's no interest by thevendor or the client 202, the booth devices 106, 107 remain as clientsand continue to provide signals 108, 109.

Referring again to FIG. 2, if a client 202 has an interest, e.g., haswhite listed the vendor associated with booth device 207, or if thevendor associated with booth device 207 has identified the client 202 asa client or potential client of interest, then additional communicationsteps begin. During these additional steps, the booth device 207 changesroles several times, between client and server roles.

As illustrated in FIG. 3, the communication process between the boothdevice and the client mobile device is described. Initially, the processbegins when the client mobile device and booth device are in range, asillustrated at 310. Thus, the client mobile device is proximate to thebooth device in terms of being physically within wireless communicationrange, for example, within several meters of the booth device. If it isconfirmed that there is communication interest between attendee andvendor, as illustrated at 320, further communication proceeds. However,if there is no communication interest, e.g., attendee has not expressedan interest in the vendor, then the process may end at 330.

Once it is confirmed that there is an interest at 320, a handshakeprocess occurs at 340 between the vendor device and the client mobiledevice. During this handshake process at 340, the booth device changesmodes from client to server, as illustrated at 350. Thus, the boothdevice switches modes from broadcasting to responding to specificrequests from the client mobile device.

In an embodiment, the two way communications between the client mobiledevice and the booth device are secured using an encryption technique.For example, the client mobile device receives an encrypted code fromthe booth device that contains a unique identifier associated with thisspecific and unique vendor at 360. The booth device receives anencrypted reply code with a unique identifier associated with thespecific and unique attendee as well at 360.

Having determined interest, performed a handshake, and secured acommunication channel, data is then exchanged in a two way communicationat 370. Now that communication is established at 370, a method to createa unique communication session identification (session ID) is provided,followed by data exchange, as illustrated at 380. One possible sessionID contains the attendee's unique identifier plus the vendor uniqueidentifier, a time/date stamp and an identifier for the informationexchanged in both directions. The unique session ID carries informationback to the manager database for action. Typical actions include but arenot necessarily limited to sending information to the attendee orproviding information to vendor. For example, demographic heuristics canbe provided in real time to the vendor.

In an embodiment, data is exchanged through the client mobile device viaan application that gives the attendee choices about which informationis of interest what information will be exchanged or sent to theattendee by the booth device. Attendee information will also be sent tothe vendor, e.g., contact information for future follow-up, based on theattendee's unique identifying information being sent as part of the twoway information exchange. During this process data is also sent to themanager database, e.g., for demographic heuristics, metrics, real timeanalytics, etc.

The exchange of data may be directed by the vendor, the attendee, orboth. For example, the attendee may request certain types of data(presentation materials, brochures, etc.) if available, and the vendormay request certain data from the attendee, e.g., contact information,demographic information, etc. As another example, a client can schedulean appointment with the vendor, e.g., by transmitting scheduling datasuch as calendar data indicating availability to the vendor to set anappointment. Database manager 214 may thereafter send both parties anotification reminder prior to the scheduled appointment.

Referring to FIG. 4, the network of booth devices is aware, i.e., abooth device is able to determine which other booth device(s) are inclose proximity, even though the booth device(s) are mobile, becauseeach is deployed with a unique ID. For example, the booth devicescommunicate with one another to form a configurable mesh network.

As shown in FIG. 4, for a given layout of an event space 401 havingvarious vendor booth locations (here, booths A, B, C, D, and E), thereare numerous paths for data exchanged between a booth device and aclient mobile device 403 to return to the manager database 414,irrespective of the communication technology leveraged (e.g., Wi-Fi®,Bluetooth® LE, subscriber identity module (SIM), IR, combinations ofthese, etc.). The network of booth devices is provided with logic foridentifying the most effective path to pass data between the managerdatabase 414 and the client mobile device 403 using the mesh network.

Various routes for the data are chosen for example based on the type ofcommunication technologies used by the booth devices, based on thecurrent volume and throughput of data, based on the currentconfiguration of the mesh network of booth devices within the eventspace, etc. As an example, if IR were used by the booth devices tocommunicate with the manager database at 414, the path may go from boothB at 405, to booth C at 415, to booth D at 416 and finally to booth Z at414 (the manager database). If Bluetooth® LE beacon communication wereused to communicate data from a client mobile device 403 to the databasemanager at 414, the path may be from client mobile device 403 to booth Bat 405 to booth C at 415 to booth D at 416 to booth E at 417 andthereafter to booth Z at 414.

In an embodiment, each unique data packet sent to the manager database414 includes a unique session ID containing the vendor ID, the attendeeID, a time/date stamp, and identifier for the type of data exchanged.Once exchange of information is complete, the booth device and theclient mobile device 403 close the session. The booth device returns toa client mode ready to serve the next client mobile device. The clientmobile device 403 returns to a mode passively listening for the nextbooth device of interest.

Unlike Wi-Fi® access point based network communication, or other fixedor static position methods, an embodiment provides a deployable networkof mobile infrastructure devices that can be created indoors, outdoors,or transition from indoors to outdoors, as illustrated in FIG. 5. Due tothe methodologies used, wired power is not necessary, thus eliminatinglong cable runs and complex set up.

For indoor and outdoor use, for example in the event space 501 of FIG.5, booth devices may be used indoors as has been described herein. Forexample, an indoor booth device 507 a is illustrated proximate todatabase manager 514.

Additionally, booth devices may be used outside as well. In the exampleof FIG. 5, devices 507 b-507 h, which may take the form of Bluetooth® LEbeacon devices (although this is not required), are placed in targetlocations where each interacts with other proximate devices. Theconfiguration of the network is essentially limitless because each boothdevice learns where it is in relation to all other booth devices in theevent space 501 during a discovery and configuration phase, i.e., itforms a mesh network with at least one other booth device or joins aformed mesh network comprising two or more other booth devices.

Depending upon the deployment location, with or without a managerdatabase 514, booth devices 507 a-507 h are configured with a program toresolve the most effective path to communicate data in the mesh network,e.g., from the database manager 514 to various vendors, between vendorsand attendees, and even out to a broader network connection.

As each booth device 507 a-507 h is deployed, a mesh of peers isestablished. The peer network configuration permits the booth devices507 a-507 h, so long as they are in close enough proximity tocommunicate with each other, to form into a mesh network. If a device of507 a-507 h fails in the field, it can simply be replaced with anadditional device that is self-configuring and self-inserting into themesh network.

Any of the booth devices 507 a-507 h can leverage a capacitive patternor radio frequency method to recognize where it is located within themesh network. Like techniques are also used to determine proximity andself-routing capabilities from peer-to-peer (or node to node). Asillustrated in FIG. 5, the mesh network could be deployed within asingle convention center tradeshow environment that extends out to anexterior environment such as a courtyard, a golf course, or other largeoutdoor venue. The mesh network formed by booth devices 507 a-507 h canalso bridge large distances between multiple convention centers orbuildings, or even be formed over many city blocks.

The mesh network formed by booth devices 507 a-507 h can not onlyprovide location data at the same elevation, but also can providelocation data at a variety of elevations, e.g., corresponding to hillson a golf course, floors in a building, or sections in a stadium orcoliseum, or elevations in any venue, stationary or moving, that areproximate to each other.

Referring back to FIG. 1 and FIG. 2, as with the attendee 102, 202described in connection with FIG. 1 and FIG. 2, the initial experiencefor a vendor is similar to a client configuration process. That is, thevendor can configure the experience. A vendor will, for example,identify the content available from the vendor to the clients andprovide that to the manager database 214. The manager database 214includes scheduling data for the event and identifies any livebroadcasts (e.g., FM broadcast or other), a schedule of events, contactinformation, etc., as submitted by the vendors. The vendor's boothdevice, e.g., booth device 207, will be provided with a unique ID thatis continuously broadcast throughout the event from a dedicated devicegiven to the vendor. This unique ID identifies the vendor to incomingclients, e.g., client 102, 202, and to other vendors in proximity. Thevendor's booth device, e.g., device 207, acts as a beacon orbroadcasting device to advertise its presence to other devices withinrange. Each vendor's ID is unique and contributes to spatialrelationship information between other vendors and to the managerdatabase 214.

In FIG. 1 for example, as a client mobile device 103 passes a booth 105,a vendor can choose to pull in attendee information via the uniqueclient ID available from the client mobile device 103. The vendor maynot automatically pass information to a client mobile device 103, forexample if the client 102 has not configured the application running onthe client mobile device 103 to express an interest in the vendor,either ahead of time as part of a set up process or manually to requestinformation in real time.

During the configuration process for a vendor, if a specific client,e.g., client 102, enters the location and passes near the booth 105, thevendor can be notified by the booth device 107. As the client mobiledevice 103 passes the booth 105, contact information can be obtained byexchange between devices 103, 107, as long as the client 102 has notblocked the vendor.

Demographic data from the event indicating performance pertinent to thevendor can be made available through the manager database 214 as data isexchanged specific to a vendor. In addition, key metrics such asstickiness (the amount of time a client spent in or around a booth),information about the client's industry or other relevant clientinformation can be provided, e.g., as anonymized information. This data,e.g., reports and visualizations of the key metrics of interest, can beprovided to the vendor or client in real time.

Given that the booth devices, e.g., devices 507 a-507 h can communicateand build up a logical spatial relationship based in their nearestneighboring booth devices, an embodiment can utilize this data togenerate dynamic maps of the event space in terms of booth devicelocation. Clients and vendors can leverage dynamic maps both indoors andoutdoors. For example, geo-positioning and location can be providedthrough a combination of the deployed network and predetermined data(e.g., known data regarding the event space dimensions), leveragingtechnologies such as SIM, Wi-Fi®, GPS, IR, Bluetooth® LE, etc. Dynamicmapping allows clients to find vendor booths and vendors to know when aclient of interest is in proximity to the vendor's booth.

The network of booth devices 507 a-507 h facilitates use of and changingbetween one communication technology and another. For example,geo-positioning location data is passed through the client mobile deviceto any of booth devices 507 a-507 h in order to offer additional dataregarding the locations of booth devices 507 a-507 h. Combining thiswith integrated device functionality, such as GPS and deployed networkfunctionality, content can be tied to a location ID and provided to bothvendors and clients through the manager database 514.

An embodiment also improves a large bottleneck for event coordination,i.e., how to manage the confirmation process at the front doors or checkpoints of an event. Many times event badges are issued to clients andparticipants. Typically worn on a lanyard, these must be individuallyinspected to assure that the client or participant is allowed to enter.An embodiment provides alternative methods using electronic devices,e.g., client mobile device 103, carried by the clients and participants.

As an example, clients with proper credentials may have a combination ofa unique color and/or code presented on their device that allows staffto easily see if a person should be allowed to enter or not. Additionalmethods include that any color onscreen, e.g., except black, are allowedto enter. Additional security could include a symbol, shape, oralphanumeric code. Attendees simply hold up their devices for easyvisibility by staff.

In an alternative embodiment, a device carried by staff authenticatesthose authorized to enter the event using a display on the staff device.The display is generated by communicating with a client's device orlanyard equipped with an identifying beacon or other signal. Thisautomates the process and eliminates the need for a client to hold up adevice, a lanyard, a badge, etc., and significantly reduces throughputwait time during credential validation.

Various aspects may be embodied as a system, method or device programproduct. Accordingly, aspects may take the form of an entirely hardwareembodiment or an embodiment including software that may all generally bereferred to herein as a “module” or “system.” Furthermore, aspects maytake the form of a device program product embodied in one or more devicereadable medium(s) having device readable program code embodiedtherewith.

The various functions described herein may be implemented usinginstructions stored on a device readable storage medium such as anon-signal storage device that are executed by a processor. A storagedevice may be, for example, an electronic device such as a random accessmemory (RAM), a read-only memory (ROM), an erasable programmableread-only memory (EPROM or Flash memory), or any suitable device. In thecontext of this document, a storage device is not a signal and“non-transitory” includes all media except signal media.

Example embodiments are described herein with reference to the figures,which illustrate example methods, devices and program products. Theactions and functionality may be implemented at least in part by programinstructions. These program instructions may be provided to a processorof a device, a special purpose information handling device, or otherprogrammable data processing device to produce a machine, such that theinstructions, which execute via a processor of the device implement thefunctions/acts specified.

What is claimed is:
 1. A system for event space communicationinfrastructure, comprising: a plurality of mobile infrastructuredevices; each of the plurality of mobile infrastructure devices beingassociated with one or more predetermined users; each of the pluralityof mobile infrastructure devices comprising a wireless communicationdevice that: broadcasts a unique identifier associated with apredetermined user; detects a response from at least one client mobiledevice; switches into a communication mode after detecting the response;and establishes data exchange with the at least one client mobiledevice.
 2. The system of claim 1, further comprising: a servercommunicating with the plurality of mobile infrastructure devices andthe at least one client mobile device, the server comprising: dataassociating the one or more predetermined users with the plurality ofmobile infrastructure devices; and data associating one or moreregistered users with the at least one client mobile device.
 3. Thesystem of claim 2, wherein each of the plurality of mobileinfrastructure devices detects one or more neighboring mobileinfrastructure devices and transmits identification data to the server.4. The system of claim 3, wherein the server resolves relative locationsof the plurality of mobile infrastructure devices using theidentification data.
 5. The system of claim 4, wherein the serverprovides map data comprising the identification data.
 6. The system ofclaim 2, wherein the server provides reporting data regarding the atleast one client mobile device detected by at least one of the pluralityof mobile infrastructure devices.
 7. The system of claim 6, wherein thereporting data comprises real-time location data regarding the at leastone client mobile device.
 8. The system of claim 6, wherein thereporting data comprises aggregated data for a period of time regardingthe at least one client mobile device.
 9. The system of claim 2, whereinthe server accesses configuration data provided by a client mobiledevice indicating authorization for automated communication from one ofthe plurality of mobile infrastructure devices.
 10. The system of claim9, wherein the one of the plurality of mobile infrastructure devicesautomatically transmits data to the client mobile device that hasauthorized automated communication in response to detecting the clientmobile device is in proximity to the one of the plurality of mobileinfrastructure devices.
 11. A method for event space communication,comprising: broadcasting, with a mobile infrastructure device, a uniqueidentifier associated with a predetermined user; detecting, at themobile infrastructure device, a response from at least one client mobiledevice; switching the mobile infrastructure device into a communicationmode after detecting the response; and establishing, between the mobileinfrastructure device and the at least one client mobile device, dataexchange.
 12. The method of claim 11, further comprising reporting, fromthe mobile infrastructure device to a server communicating with themobile infrastructure device, that the at least one client mobile devicehas been detected.
 13. The method of claim 12, further comprising:detecting, with the mobile infrastructure device, one or moreneighboring mobile infrastructure devices; and resolving relativelocations of the mobile infrastructure device and the one or moreneighboring mobile infrastructure devices.
 14. A method for event spacecommunication, comprising: providing, to a client mobile device, anapplication comprising predetermined user information; receiving, fromthe client mobile device, an indication of interest in at least onepredetermined user included in the predetermined user information;identifying, using a processor, a predetermined user based on theindication of interest; providing, to the client mobile device, a uniqueidentifier of the predetermined user; and thereafter communicating, to amobile infrastructure device assigned to the predetermined user, aunique identifier of the client mobile device.
 15. The method of claim14, further comprising: transmitting, to a device associated with theunique identifier of the predetermined user, data; wherein the data isselected from the group consisting of a number of client mobile devicesproviding indications of interest; and a number of clients mobiledevices detected by the mobile infrastructure device assigned to thepredetermined user.
 16. The method of claim 15, wherein the transmittingproceeds according to a predetermined timing policy.
 17. A mobileinfrastructure device for event space communication, comprising: acommunication device that broadcasts a unique identifier associated witha predetermined user; a processor that detects a response from at leastone client mobile device and switches into a communication mode afterdetecting the response; and a communication device that, after detectingthe response from the at least one client device, establishes dataexchange with the at least one client mobile device.
 18. The mobileinfrastructure device of claim 17, wherein the data exchange isencrypted using a code unique to a communication session between themobile infrastructure device and the at least one client device.
 19. Themobile infrastructure device of claim 17, wherein the data exchangecomprises data selected from the group consisting of contact data, audiodata, and video data.
 20. The mobile infrastructure device of claim 17,wherein the processor: detects one or more other mobile infrastructuredevices; and forms or joins a mesh network comprising the one or moreother mobile infrastructure devices.